RAN Condition and Cell Composite Load Indicators

ABSTRACT

An apparatus of a management service equipment includes processing circuitry. To configure the management service equipment for measuring a plurality of key performance indicators (KPIs) in a 5G network with a plurality of network functions (NFs), the processing circuitry is to retrieve using a data analytic function of the management service equipment, a plurality of performance measurements associated with a cell of a radio access network (RAN) within the 5G network. A KPI of the plurality of KPIs associated with the cell is generated using the data analytic function of the management service equipment, based on the plurality of performance measurements. The KPI is encoded for transmission to a service application executing on a user equipment (UE) active within the cell of the RAN or executing within a cloud architecture.

PRIORITY CLAIM

This application claims the benefit of priority to U.S. ProvisionalPatent Application Ser. No. 62/716,443, filed Aug. 9, 2018, and entitled“RAN CONDITION AND CELL COMPOSITE LOAD KPIS,” which provisional patentapplication is incorporated herein by reference in its entirety.

TECHNICAL FIELD

Aspects pertain to wireless communications. Some aspects relate towireless networks including 3GPP (Third Generation Partnership Project)is networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTEAdvanced) networks, and fifth-generation (5G) networks including 5G newradio (NR) (or 5G-NR) networks and 5G-LTE networks. Other aspects aredirected to systems and methods for providing key performance indicators(KPIs), such as radio access network (RAN) condition and cell compositeload indicators in 5G networks.

BACKGROUND

Mobile communications have evolved significantly from early voicesystems to today's highly sophisticated integrated communicationplatform. With the increase in different types of devices communicatingwith various network devices, usage of 3GPP LTE systems has increased.The penetration of mobile devices (user equipment or UEs) in modernsociety has continued to drive demand for a wide variety of networkeddevices in a number of disparate environments. Fifth generation (5G)wireless systems are forthcoming and are expected to enable even greaterspeed, connectivity, and usability. Next generation 5G networks (or NRnetworks) are expected to increase throughput, coverage, and robustnessand reduce latency and operational and capital expenditures. 5G-NRnetworks will continue to evolve based on 3GPP LTE-Advanced withadditional potential new radio access technologies (RATs) to enrichpeople's lives with seamless wireless connectivity solutions deliveringfast, rich content and services. As current cellular network frequencyis saturated, higher frequencies, such as millimeter wave (mmWave)frequency, can be beneficial due to their high bandwidth.

Potential LTE operation in the unlicensed spectrum includes (and is notlimited to) the LTE operation in the unlicensed spectrum via dualconnectivity (DC), or DC-based LAA, and the standalone LTE system in theunlicensed spectrum, according to which LTE-based technology solelyoperates in unlicensed spectrum without requiring an “anchor” in thelicensed spectrum, called MulteFire. MulteFire combines the performancebenefits of LTE technology with the simplicity of Wi-Fi-likedeployments.

Further enhanced operation of LTE systems in the licensed as well asunlicensed spectrum is expected in future releases and 5G systems. Suchenhanced operations can include techniques for providing KPIs, such asRAN condition and cell composite load indicators in 5G networks.

BRIEF DESCRIPTION OF THE FIGURES

In the figures, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. Like numerals havingdifferent letter suffixes may represent different instances of similarcomponents. The figures illustrate generally, by way of example, but notby way of limitation, various aspects discussed in the present document.

FIG. 1A illustrates an architecture of a network, in accordance withsome aspects.

FIG. 1B and FIG. 1C illustrate a non-roaming 5G system architecture inaccordance with some aspects.

FIG. 2 illustrates components of an exemplary 5G-NR architecture withcontrol unit control plane (CU-CP)—control unit user plane (CU-UP)separation, in accordance with some aspects.

FIG. 3 illustrates generation of data analytic KPIs by a data analyticfunction within a management system of a 5G network, in accordance withsome aspects.

FIG. 4 illustrates a use case for a RAN condition KPI use in connectionwith outer navigation assistance, in accordance with some aspects.

FIG. 5 illustrates a block diagram of a communication device such as anevolved Node-B (eNB), a new generation Node-B (gNB), an access point(AP), a wireless station (STA), a mobile station (MS), or a userequipment (UE), in accordance with some aspects.

DETAILED DESCRIPTION

The following description and the drawings sufficiently illustrateaspects to enable those skilled in the art to practice them. Otheraspects may incorporate structural, logical, electrical, process, andother changes. Portions and features of some aspects may be included in,or substituted for, those of other aspects. Aspects set forth in theclaims encompass all available equivalents of those claims.

FIG. 1A illustrates an architecture of a network in accordance with someaspects. The network 140A is shown to include user equipment (UE) 101and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g.,handheld touchscreen mobile computing devices connectable to one or morecellular networks) but may also include any mobile or non-mobilecomputing device, such as Personal Data Assistants (PDAs), pagers,laptop computers, desktop computers, wireless handsets, drones, or anyother computing device including a wired and/or wireless communicationsinterface. The UEs 101 and 102 can be collectively referred to herein asUE 101, and UE 101 can be used to perform one or more of the techniquesdisclosed herein.

Any of the radio links described herein (e.g., as used in the network140A or any other illustrated network) may operate according to anyexemplary radio communication technology and/or standard.

LTE and LTE-Advanced are standards for wireless communications ofhigh-speed data for UE such as mobile telephones. In LTE-Advanced andvarious wireless systems, carrier aggregation is a technology accordingto which multiple carrier signals operating on different frequencies maybe used to carry communications for a single UE, thus increasing thebandwidth available to a single device. In some aspects, carrieraggregation may be used where one or more component carriers operate onunlicensed frequencies.

Aspects described herein can be used in the context of any spectrummanagement scheme including, for example, dedicated licensed spectrum,unlicensed spectrum, (licensed) shared spectrum (such as Licensed SharedAccess (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and furtherfrequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and furtherfrequencies).

Aspects described herein can also be applied to different Single Carrieror OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-basedmulticarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio)by allocating the OFDM carrier data bit vectors to the correspondingsymbol resources.

In some aspects, any of the UEs 101 and 102 can comprise anInternet-of-Things (IoT) UE or a Cellular loT (CloT) UE, which cancomprise a network access layer designed for low-power IoT applicationsutilizing short-lived UE connections. In some aspects, any of the UEs101 and 102 can include a narrowband (NB) IoT UE (e.g., such as anenhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An IoTUE can utilize technologies such as machine-to-machine (M2M) ormachine-type communications (MTC) for exchanging data with an MTC serveror device via a public land mobile network (PLMN), Proximity-BasedService (ProSe) or device-to-device (D2D) communication, sensornetworks, or loT networks. The M2M or MTC exchange of data may be amachine-initiated exchange of data. An loT network includesinterconnecting IoT UEs, which may include uniquely identifiableembedded computing devices (within the Internet infrastructure), withshort-lived connections. The IoT UEs may execute background applications(e.g., keep-alive messages, status updates, etc.) to facilitate theconnections of the IoT network.

In some aspects, any of the UEs 101 and 102 can include enhanced MTC(eMTC) UEs or further enhanced MTC (FeMTC) UEs.

The UEs 101 and 102 may be configured to connect, e.g., communicativelycouple, with a radio access network (RAN) 110. The RAN 110 may be, forexample, an Evolved Universal Mobile Telecommunications System (UMTS)Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), orsome other type of RAN. The UEs 101 and 102 utilize connections 103 and104, respectively, each of which comprises a physical communicationsinterface or layer (discussed in further detail below); in this example,the connections 103 and 104 are illustrated as an air interface toenable communicative coupling, and can be consistent with cellularcommunications protocols, such as a Global System for MobileCommunications (GSM) protocol, a code-division multiple access (CDMA)network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular(POC) protocol, a Universal Mobile Telecommunications System (UMTS)protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth generation(5G) protocol, a New Radio (NR) protocol, and the like.

In an aspect, the UEs 101 and 102 may further directly exchangecommunication data via a ProSe interface 105. The ProSe interface 105may alternatively be referred to as a sidelink interface comprising oneor more logical channels, including but not limited to a PhysicalSidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel(PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a PhysicalSidelink Broadcast Channel (PSBCH).

The UE 102 is shown to be configured to access an access point (AP) 106via connection 107. The connection 107 can comprise a local wirelessconnection, such as, for example, a connection consistent with any IEEE802.11 protocol, according to which the AP 106 can comprise a wirelessfidelity (WiFi@) router. In this example, the AP 106 is shown to beconnected to the Internet without connecting to the core network of thewireless system (described in further detail below).

The RAN 110 can include one or more access nodes that enable theconnections 103 and 104. These access nodes (ANs) can be referred to asbase stations (BSs), NodeBs, evolved NodeBs (eNBs), Next GenerationNodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations(e.g., terrestrial access points) or satellite stations providingcoverage within a geographic area (e.g., a cell). In some aspects, thecommunication nodes 111 and 12 can be transmission/reception points(TRPs). In instances when the communication nodes 111 and 112 are NodeBs(e.g., eNBs or gNBs), one or more TRPs can function within thecommunication cell of the NodeBs. The RAN 110 may include one or moreRAN nodes for providing macrocells, e.g., macro RAN node 11, and one ormore RAN nodes for providing femtocells or picocells (e.g., cells havingsmaller coverage areas, smaller user capacity, or higher bandwidthcompared to macrocells), e.g., low power (LP) RAN node 112.

Any of the RAN nodes 111 and 112 can terminate the air interfaceprotocol and can be the first point of contact for the UEs 101 and 102.In some aspects, any of the RAN nodes 111 and 112 can fulfill variouslogical functions for the RAN 110 including, but not limited to, radionetwork controller (RNC) functions such as radio bearer management,uplink and downlink dynamic radio resource management and data packetscheduling, and mobility management. In an example, any of the nodes 111and/or 112 can be a new generation node-B (gNB), an evolved node-B(eNB), or another type of RAN node.

The RAN 110 is shown to be communicatively coupled to a core network(CN) 120 via an S1 interface 113. In aspects, the CN 120 may be anevolved packet core (EPC) network, a NextGen Packet Core (NPC) network,or some other type of CN (e.g., as illustrated in reference to FIGS.1B-1I). In this aspect, the S1 interface 113 is split into two parts:the S1-U interface 114, which carries traffic data between the RAN nodes111 and 112 and the serving gateway (S-GW) 122, and the S1-mobilitymanagement entity (MME) interface 115, which is a signaling interfacebetween the RAN nodes 111 and 112 and MMEs 121.

In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, thePacket Data Network (PDN) Gateway (P-GW) 123, and a home subscriberserver (HSS) 124. The MMEs 121 may be similar in function to the controlplane of legacy Serving General Packet Radio Service (GPRS) SupportNodes (SGSN). The MMEs 121 may manage mobility aspects in access such asgateway selection and tracking area list management. The HSS 124 maycomprise a database for network users, including subscription-relatedinformation to support the network entities' handling of communicationsessions. The CN 120 may comprise one or several HSSs 124, depending onthe number of mobile subscribers, on the capacity of the equipment, onthe organization of the network, etc. For example, the HSS 124 canprovide support for routing/roaming, authentication, authorization,naming/addressing resolution, location dependencies, etc.

The S-GW 122 may terminate the S1 interface 113 towards the RAN 110, androutes data packets between the RAN 110 and the CN 120. In addition, theS-GW 122 may be a local mobility anchor point for inter-RAN nodehandovers and also may provide an anchor for inter-3GPP mobility. Otherresponsibilities of the S-GW 122 may include a lawful intercept,charging, and some policy enforcement.

The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123may route data packets between the EPC network 120 and external networkssuch as a network including the application server 184 (alternativelyreferred to as application function (AF)) via an Internet Protocol (IP)interface 125. The P-GW 123 can also communicate data to other externalnetworks 131A, which can include the Internet, IP multimedia subsystem(IPS) network, and other networks. Generally, the application server 184may be an element offering applications that use IP bearer resourceswith the core network (e.g., UMTS Packet Services (PS) domain, LTE PSdata services, etc.). In this aspect, the P-GW 123 is shown to becommunicatively coupled to an application server 184 via an IP interface125. The application server 184 can also be configured to support one ormore communication services (e.g., Voice-over-Internet Protocol (VoIP)sessions, PTT sessions, group communication sessions, social networkingservices, etc.) for the UEs 101 and 102 via the CN 120.

The P-GW 123 may further be a node for policy enforcement and chargingdata collection. Policy and Charging Rules Function (PCRF) 126 is thepolicy and charging control element of the CN 120. In a non-roamingscenario, in some aspects, there may be a single PCRF in the Home PublicLand Mobile Network (HPLMN) associated with a UE's Internet ProtocolConnectivity Access Network (IP-CAN) session. In a roaming scenario witha local breakout of traffic, there may be two PCRFs associated with aUE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a VisitedPCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). ThePCRF 126 may be communicatively coupled to the application server 184via the P-GW 123.

In some aspects, the communication network 140A can be an IoT network.One of the current enablers of IoT is the narrowband-IoT (NB-IoT).

A NG system architecture can include the RAN 110 and a 5G network core(5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBsand NG-eNBs. The core network 120 (e.g., a 5G core network or 5GC) caninclude an access and mobility function (AMF) and/or a user planefunction (UPF). The AMF and the UPF can be communicatively coupled tothe gNBs and the NG-eNBs via NG interfaces. More specifically, in someaspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-Cinterfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBscan be coupled to each other via Xn interfaces.

In some aspects, the NG system architecture can use reference pointsbetween various nodes as provided by 3GPP Technical Specification (TS)23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNBs andthe NG-eNBs can be implemented as a base station, a mobile edge server,a small cell, a home eNB, and so forth. In some aspects, a gNB can be amaster node (MN) and NG-eNB can be a secondary node (SN) in a 5Garchitecture.

FIG. 1B illustrates a non-roaming 5G system architecture in accordancewith some aspects. Referring to FIG. 1B, there is illustrated a 5Gsystem architecture 140B in a reference point representation. Morespecifically, UE 102 can be in communication with RAN 110 as well as oneor more other 5G core (5GC) network entities. The 5G system architecture140B includes a plurality of network functions (NFs), such as access andmobility management function (AMF) 132, session management function(SMF) 136, policy control function (PCF) 148, application function (AF)150, user plane function (UPF) 134, network slice selection function(NSSF) 142, authentication server function (AUSF) 144, and unified datamanagement (UDM)/home subscriber server (HSS) 146. The UPF 134 canprovide a connection to a data network (DN) 152, which can include, forexample, operator services, Internet access, or third-party services.The AMF 132 can be used to manage access control and mobility and canalso include network slice selection functionality. The SMF 136 can beconfigured to set up and manage various sessions according to a networkpolicy. The UPF 134 can be deployed in one or more configurationsaccording to a desired service type. The PCF 148 can be configured toprovide a policy framework using network slicing, mobility management,and roaming (similar to PCRF in a 4G communication system). The UDM canbe configured to store subscriber profiles and data (similar to an HSSin a 4G communication system).

In some aspects, the 5G system architecture 140B includes an IPmultimedia subsystem (IMS) 168B as well as a plurality of IP multimediacore network subsystem entities, such as call session control functions(CSCFs). More specifically, the IMS 168B includes a CSCF, which can actas a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, anemergency CSCF (E-CSCF) (not illustrated in FIG. 1B), or interrogatingCSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the firstcontact point for the UE 102 within the IM subsystem (IMS) 168B. TheS-CSCF 164B can be configured to handle the session states in thenetwork, and the E-CSCF can be configured to handle certain aspects ofemergency sessions such as routing an emergency request to the correctemergency center or PSAP. The I-CSCF 166B can be configured to functionas the contact point within an operator's network for all IMSconnections destined to a subscriber of that network operator, or aroaming subscriber currently located within that network operator'sservice area. In some aspects, the I-CSCF 166B can be connected toanother IP multimedia network 170E, e.g. an IMS operated by a differentnetwork operator.

In some aspects, the UDM/HSS 146 can be coupled to an application server160E, which can include a telephony application server (TAS) or anotherapplication server (AS). The AS 160B can be coupled to the IMS 168B viathe S-CSCF 164B or the I-CSCF 166B.

A reference point representation shows that interaction can existbetween corresponding NF services. For example, FIG. 1B illustrates thefollowing reference points: N1 (between the UE 102 and the AMF 132), N2(between the RAN 110 and the AMF 132), N3 (between the RAN 110 and theUPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152),N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown),N10 (between the UDM 146 and the SMF 136, not shown), N11 (between theAMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and theAMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, notshown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148and the AMF 132 in case of a non-roaming scenario, or between the PCF148 and a visited network and AMF 132 in case of a roaming scenario, notshown), N16 (between two SMFs, not shown), and N22 (between AMF 132 andNSSF 142, not shown). Other reference point representations not shown inFIG. 1E can also be used.

FIG. 1C illustrates a 5G system architecture 140C and a service-basedrepresentation. In addition to the network entities illustrated in FIG.1B, system architecture 140C can also include a network exposurefunction (NEF) 154 and a network repository function (NRF) 156. In someaspects, 5G system architectures can be service-based and interactionbetween network functions can be represented by correspondingpoint-to-point reference points Ni or as service-based interfaces.

In some aspects, as illustrated in FIG. 1C, service-basedrepresentations can be used to represent network functions within thecontrol plane that enable other authorized network functions to accesstheir services. In this regard, 5G system architecture 140C can includethe following service-based interfaces: Namf 158H (a service-basedinterface exhibited by the AMF 132), Nsmf 1581 (a service-basedinterface exhibited by the SMF 136), Nnef 158B (a service-basedinterface exhibited by the NEF 154), Npcf 158D (a service-basedinterface exhibited by the PCF 148), a Nudm 158E (a service-basedinterface exhibited by the UDM 146), Naf 158F (a service-based interfaceexhibited by the AF 150), Nnrf 158C (a service-based interface exhibitedby the NRF 156), Nnssf 158A (a service-based interface exhibited by theNSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf)not shown in FIG. 1C can also be used.

FIG. 2 illustrates components of an exemplary 5G-NR architecture 200with a control plane (CP)—user plane (UP) separation, in accordance withsome aspects. Referring to FIG. 2 , the 5G-NR architecture 200 caninclude a 5G core 212 and NG-RAN 214. The NG-RAN 214 can include one ormore gNBs such as gNB 128A and 128B (which can be the same as gNB 128).The 5GC 212 and the NG-RAN 214, in some aspects, may be similar or thesame as the 5GC 120 and the NG-RAN 110 of FIG. 1B, respectively. In someaspects, network elements of the NG-RAN 214 may be split into centraland distributed units, and different central and distributed units, orcomponents of the central and distributed units, may be configured forperforming different protocol functions.

In some aspects, the gNB 128B can comprise or be split into one or moreof a gNB Central Unit (gNB-CU) 202 and a gNB Distributed Unit (gNB-DU)204, 206. Additionally, the gNB 128B can comprise or be split into oneor more of a gNB-CU-Control Plane (gNB-CU-CP) 208 and a gNB-CU-UserPlane (gNB-CU-UP) 210. The gNB-CU 202 is a logical node configured tohost the radio resource control layer (RRC), service data adaptationprotocol (SDAP) layer and packet data convergence protocol layer (PDCP)protocols of the gNB or RRC, and PDCP protocols of the E-UTRA-NR gNB(en-gNB) that controls the operation of one or more gNB-DUs. The gNB-DU(e.g., 204 or 206) is a logical node configured to host the radio linkcontrol layer (RLC), medium access control layer (MAC) and physicallayer (PHY) layers of the gNB 128A, 128B or en-gNB, and its operation isat least partly controlled by gNB-CU 202. In some aspects, one gNB-DU(e.g., 204) can support one or multiple cells.

The gNB-CU 202 comprises a gNB-CU-Control Plane (gNB-CU-CP) entity 208and a gNB-CU-User Plane entity 210. The gNB-CU-CP 208 is a logical nodeconfigured to host the RRC and the control plane part of the PDCPprotocol of the gNB-CU 202 for an en-gNB or a gNB. The gNB-CU-UP 210 isa logical (or physical) node configured to host the user plane part ofthe PDCP protocol of the gNB-CU 202 for an en-gNB, and the user planepart of the PDCP protocol and the SDAP protocol of the gNB-CU 202 for agNB.

The gNB-CU 202 and the gNB-DU 204, 206 can communicate via the F1interface, and the gNB 128A can communicate with the gNB-CU 202 via theXn-C interface. The gNB-CU-CP 208 and the gNB-CU-UP 210 can communicatevia the E1 interface. Additionally, the gNB-CU-CP 208 and the gNB-DU204, 206 can communicate via the F1-C interface, and the gNB-DU 204, 206and the gNB-CU-UP 210 can communicate via the F1-U interface.

In some aspects, the gNB-CU 202 terminates the F1 interface connectedwith the gNB-DU 204, 206, and in other aspects, the gNB-DU 204, 206terminates the F1 interface connected with the gNB-CU 202. In someaspects, the gNB-CU-CP 208 terminates the E1 interface connected withthe gNB-CU-UP 210 and the F1-C interface connected with the gNB-DU 204,206. In some aspects, the gNB-CU-UP 210 terminates the E1 interfaceconnected with the gNB-CU-CP 208 and the F1-U interface connected withthe gNB-DU 204, 206.

In some aspects, the F1 interface is a point-to-point interface betweenendpoints and supports the exchange of signaling information betweenendpoints and data transmission to the respective endpoints. The F1interface can support control plane and user plane separation andseparate the Radio Network Layer and the Transport Network Layer. Insome aspects, the E1 interface is a point-to-point interface between agNB-CU-CP and a gNB-CU-UP and supports the exchange of signalinginformation between endpoints. The E1 interface can separate the RadioNetwork Layer and the Transport Network Layer, and in some aspects, theE1 interface may be a control interface not used for user dataforwarding.

In certain aspects, for EN-DC, the S1-U interface and an X2 interface(e.g., X2-C interface) for a gNB, consisting of a gNB-CU and gNB-DUs,can terminate in the gNB-CU.

In some aspects, gNB 128B supporting CP/UP separation, includes a singleCU-CP entity 208, multiple CU-UP entities 210, and multiple DU entities204, . . . , 206, with all entities being configured for network sliceoperation. As illustrated in FIG. 2 , each DU entity 204, . . . , 206can have a single connection with the CU-CP 208 via a F1-C interface.Each DU entity 204, . . . , 206 can be connected to multiple CU-UPentities 210 using F1-U interfaces. The CU-CP entity 208 can beconnected to multiple CU-UP entities 210 via E1 interfaces. Each DUentity 204, . . . , 206 can be connected to one or more UEs, and theCU-UP entities 210 can be connected to a user plane function (UPF) andthe 5G core 212.

In some aspects, applications for 5G networks can be configured tosupport autonomous driving that may need ultra-low latency and highreliability communications, as issues in the RAN (e.g., such as highlatency communications) can have the possibility to cause propertydamage and body injury. When the auto navigation application (e.g., anavigation service application being executed on a user equipment) firstsets up the route for traveling to a desired destination, the autonavigation application may use information (such as KPIs) from thenetwork to assist the vehicle operator in advance in avoiding travelinto the areas that may experience (or are experiencing) RAN issues(e.g., as indicated or deduced from the KPIs communicated by thenetwork, such as by a network management service).

In some aspects, 5G services (e.g., enhanced mobile broadband (eMBB),ultra reliable low latency communications (URLLC), or massivemachine-type communications (mMTC)) may be characterized by high-speedhigh data volume, low-speed ultra-low latency, and infrequenttransmission of low data volume from a large number of emerging smartdevices, respectively. To support the wide range of QoS levels, 5Gnetworks may be automatically tuned (e.g., using one or more KPIs asdiscussed herein) in order to maintain the optimal performance. With theadvances of artificial intelligence (AI) and big data, RAN condition andcell composite load KPIs can be collected, as discussed herein, andanalyzed to determine the status and traffic patterns of 5G networks(e.g., one or more neighboring cells associated with a navigationroute), based on time and locations (when and where) the KPIs werecollected to enable analytic applications to predict potential issues,and to plan a solution in advance and resolve the issues (e.g.,navigation-related issues) before happening. Techniques disclosed hereindiscuss the use of the RAN condition KPI and the cell composite load KPI(e.g., by analytic applications) to assist auto navigation (or otherapplications or services) as well as 5G network optimization.

In some aspects, existing 3GPP technical specifications (TSs) (e.g., TS28.552) may be supplemented to define E2E delay measurements and mayalso include clarifications on how the measurements are counted andwhich network functions (NFs) are involved to support the E2Emeasurements and determination of one or more KPTs based on suchmeasurements.

Examples of 5G NFs are illustrated in FIG. 1F. Referring again to FIG.1F, in some aspects, the 5G network 140F may include a management system(or management service) 190, which is configured to offer managementcapabilities within the 5G network 140F. These management capabilitiesmay be accessed by management service consumers via a service interface(e.g., 196), which may be composed of individually specified managementservice components. In this regard, the management system 190 may beconfigured to communicate with each of the NFs as well as other networkentities within the network 140F, except the UE 101 (e.g., including thenetwork entities within the dashed area in FIG. 1F), via the serviceinterface 196. In some aspects, the management system 190 may beconfigured based on 3GPP TS 28.533 (v16.0.0).

In some aspects, the management system 190 may include managementfunctions (MFs) 192, . . . , 194. In some aspects, at least one of theMFs (e.g., MF 192) may be configured as a service producer, performingone or to more E2E performance measurement functions. In some aspects,at least another of the MFs (e.g., MF 193) can be configured as a dataanalytic function (DAF) 193. In some aspects, the service producer(e.g., 198) and the DAF 193 may be implemented within at least one ofthe NFs within the 5G network 140F.

In some aspects, the DAF 193 can be configured to receive performancemeasurements, alarm information, and/or configuration information anddetermine one or more data analytic KPIs associated with the 5G network140F. Example KPIs which can be determined by the DAF 193 include a RANcondition KPI and a cell composite load KPI, which can include an uplinkcell composite load KPI in a downlink cell composite load KPI.

In some aspects, the following measurement definition template(described in greater detail in 3GPP TS 32.404 V15.0.0) may be used inconnection with data analytic KPI determination by the DAF 193:

Measurement Name

(a) Description. (b) Collection Method—contains the form in which themeasurement data is obtained, including: CC (Cumulative Counter); GAUGE(dynamic variable), used when data being measured can vary up or downduring the period of measurement; DER (Discrete Event Registration),when data related to a particular event are captured every nth event isregistered, where n can be 1 or larger; SI (Status Inspection); TF(Transparent Forwarding); and OM (Object Mapping).

(c) Condition—contains the condition which causes the measurement resultdata to be updated. (d) Measurement Result (measured value(s), Units).This subclause contains a description of expected result value(s) (e.g.,a single integer value). If a measurement is related to “external”technologies, this subclause shall also give a brief reference to otherstandard bodies. (e) Measurement Type. This subclause contains a shortform of the measurement name specified in the header, which is used toidentify the measurement type in the result files.

(f) Measurement Object Class. This subclause describes the measuredobject class (e.g. UtranCell, RncFunction, SgsnFunction). (g) SwitchingTechnology. This subclause contains the Switching domain(s) thismeasurement is applicable to i.e. Circuit Switched and/or PacketSwitched. (h) Generation. The generation determines if it concerns aGSM, UMTS, EPS, 5GS, combined (GSM+UMTS+EPS+5GS) or IMS measurement. (i)Purpose. This optional clause aims at describing who will be using themeasurement.

FIG. 3 illustrates generation of data analytic KPIs by a data analyticfunction within a management system of a 5G network, in accordance withsome aspects. Referring to FIG. 3 , diagram 300 illustrates generationof data analytic KPIs 304. More specifically, the data analytic function193 within the management system 190 receives management and data 302,which can be used to perform KPI calculations 199 in order to generatedata analytic KPIs 304. The data analytic KPIs 304 can include RANcondition KPI and cell composite load KPI, as well as other KPIsindicative of network conditions and status of one or more entitieswithin the 5G network 140F. In some aspects, the management data 302 caninclude performance measurements (e.g., a number of handover failures, anumber of RRC connection setup failures, a number of RACH failures,packet loss rate, and so forth), alarm information (e.g., an alarm ornotification generated in connection with a cell overload, networktraffic throughput decrease below threshold, a number of networkfailures reaching a threshold, or other system or configuration alarms),as well as configuration information related to condition of one or moreNR cells within the 5G network. In some aspects, the management data 302can be generated by one or more of the NFs associated with the 5Gnetwork 140F and communicated to the data analytic function 193 or madeavailable (e.g., stored in network storage) for retrieval by the dataanalytic function 193.

In some aspects, the data analytic KPIs 304 are communicated to ananalytic application 306, which can be a management function within themanagement system 190, a network function within the 5G network 140F, ora standalone application such as a service application executing on anetwork device in the edge cloud or a public cloud. In some aspects, thedata analytic function 193 can generate a RAN condition KPI, which canbe described using the following subsections a)-j) of the abovementioned template:

RAN condition KPI.

a) This KPI indicates the condition of an NR cell that can be used toassist the applications, such as auto navigation. b) This KPI describesthe condition of an NR cell. c) This KPI is generated from the analysisof performance measurements and alarms related to the condition of an NRcell. In some aspects, the value of the KPI is an integer number torepresent the RAN condition of a cell and may include the followingvalues: 0: indicating a healthy/normal functioning cell; 1: out ofservice cell; 2: capacity constraint (e.g., an overloaded cell); and 3:capability constraint (e.g., the cell does not support latencyrequirement). In some aspects, the above-listed integer values may beextended to represent additional conditions. d) RanCondition. e) Thespecific performance measurements used for deriving this KPI are up toimplementation. f) 5GS. g) Condition. h) Integer. i) N/A. j) This KPIcan be used to assist an application to perform auto navigation inautonomous driving aspects, as discussed in connection with FIG. 4 .

FIG. 4 illustrates a use case 400 for a RAN condition KPI use inconnection with outer navigation assistance, in accordance with someaspects. A major application for 5G networks is to support autonomousdriving that may use ultra-low latency and high reliability, as issuesin the RAN can have the possibility to cause property damage and bodyinjury. When an auto navigation application first sets up a navigationroute for a car to reach a destination, it can be configured to avoiddirecting the car from traveling into the areas that may experience RANissues in advance. For example, if a cell is overloaded with usertraffic, experiencing an outage, or not able to support the latencyrequirement, then this cell may be removed from the planned navigationroute.

In some aspects and in connection with autonomous driving, a RANcondition KPI per cell (e.g., for each of the cells 406-424) may becollected, and made available to assist an autonomous driving vehicle atposition 402A to reach a destination 402B, and in controlling the autonavigation from position 402A to position 402B. Based on a cellidentifier received with the RAN condition KPI, the application knowsthe neighbor relation between cells 406-424. Based on the cell where thecar is located, the autonomous driving application (or a navigationapplication) knows the RAN condition of neighboring cells along aplanned route, and may change the route accordingly, as the RANconditions may change along the way when the car is traveling.

For example, FIG. 4 illustrates a vehicle traveling from position 402Ain cell 406 to position 402B in cell 422. It may be detected (e.g., viaa received RAN condition KPI) that cell 416 is either overloaded withuser traffic, is experiencing an outage, or it is not able to supportthe latency requirement of the traveling vehicle. Therefore, the autonavigation application plans the navigation route to detour and passthrough cells 414 and 420. In some aspects, the data analytic function193 can generate a cell composite load KPI, which can include an uplink(UL) cell composite load KPI and/or a downlink (DL) cell composite loadKPI, which KPIs can be described using the following subsections a)—j)of the above mentioned template:

UL cell composite load KPI.

a) This KPI is intended to be used to analyze the traffic trend of 5Gnetworks. b) This KPI describes the ULcomposite load of a NR cell. c)This KPI is generated from the analysis of management data such asperformance measurements, alerts, and configuration information (e.g.PRB usage, an average number of active UEs, IP/data throughput in theUL, resource usage, and so forth). d) ulCellCompositeLoad. e) Thespecific performance measurements used for deriving this KPI are up toimplementation. f) 5GS. g) Condition. h) Integer. i) N/A. j) This KPIcan be used to understand the status and traffic patterns of 5Gnetworks.

DL cell composite load KPI.

a) This KPI is intended to be used to analyze the traffic trend of 5Gnetworks. b) This KPI describes the DLcomposite load of a NR cell. c)This KPI is generated from the analysis of management data such asperformance measurements, alerts, and configuration information (e.g.,PRB usage, an average number of active UEs, IP/data throughput in theDL, resource usage, and so forth). d) dlCellCompositeLoad. e) Thespecific performance measurements used for deriving this KPI are up toimplementation. f) 5GS. g) Condition. h) Integer. i) N/A. j) This KPIcan be used to understand the status and traffic patterns of 5Gnetworks.

In some aspects, with the advances of AI and big data, cell compositeload KPIs can be collected and analyzed to understand the status andtraffic patterns of 5G networks, based on time and locations when andwhere the KPI is collected to enable analytic applications to predictthe potential issues, and to plan a solution in advance to resolve theissues before happening.

A service producer supported by one or more processors is configured toobtain management data, analyze the management data, generate themanagement data analytical KPI(s), and/or report the management dataanalytical KPI(s). The management data includes performancemeasurements, alarm information, and/or configuration information. Themanagement data analytical KPI is a RAN condition KPI that indicates theRAN condition for a cell. The RAN condition KPI is generated from themanagement data, including, but not limited to, performancemeasurements, alarms, and/or configuration data related to the conditionof a cell. The RAN condition KPI includes, but is not limited to, thefollowing values: 0: healthy cell; 1: out of service cell; 2: capacityconstraint (e.g., overloaded cell); and 3: capability constraint (e.g.,the cell does not support latency requirement). The uplink cellcomposite load KPI is generated from the management data (e.g., PRBusage, an average active UE, IP throughput in the uplink, resourceusages, and so forth). The downlink cell composite load KPI is generatedfrom management data (e.g., PRB usage, average number of active UEs, IPthroughput in the downlink, resource usage, and so forth). The downlinkcell composite load KPI and uplink cell composite load KPI can be usedby analytic applications to predict the potential issues, and to plan asolution in advance to resolve the issues before happening.

An analytic application acting as the service consumer supported by oneor more processors, is configured to receive an analytic KPI, analyzethe analytic KPI, and perform an action to mitigate an issue handled bythe application. The analytic application is aware of a neighborrelation between cells. Based on the cell where the car is located, theanalytic application knows the RAN condition of the neighboring cells,and may change the route, based on the RAN condition determined based ona received KPI. The analytic application can be configured to avoidcells with RAN condition of out of service, capacity constraint (e.g.,overloaded), or capability constraint (e.g., does not support latencyrequirement). The analytic application can be configured to analyze theuplink cell composite load KPI and downlink cell composite load KPI tounderstand the status and traffic patterns of 5G networks, based on timeand locations when and where the KPI is collected. The analyticapplication can be configured to generate a prediction of potentialissues, and plan a solution in advance to resolve the issues beforehappening (e.g., dynamically change a navigation route for aself-driving vehicle based on received KPIs associated with condition ofone or more cells the planned navigation route is passing through).

FIG. 5 illustrates a block diagram of a communication device such as anevolved Node-B (eNB), a next generation Node-B (gNB), an access point(AP), a wireless station (STA), a mobile station (MS), or a userequipment (UE), in accordance with some aspects and to perform one ormore of the techniques disclosed herein. In alternative aspects, thecommunication device 500 may operate as a standalone device or may beconnected (e.g., networked) to other communication devices.

Circuitry (e.g., processing circuitry) is a collection of circuitsimplemented intangible entities of the device 500 that include hardware(e.g., simple circuits, gates, logic, etc). Circuitry membership may beflexible over time. Circuitries include members that may, alone or incombination, perform specified operations when operating. In an example,the hardware of the circuitry may be immutably designed to carry out aspecific operation (e.g., hardwired). In an example, the hardware of thecircuitry may include variably connected physical components (e.g.,execution units, transistors, simple circuits, etc.) including amachine-readable medium physically modified (e.g., magnetically,electrically, moveable placement of invariant massed particles, etc.) toencode instructions of the specific operation.

In connecting the physical components, the underlying electricalproperties of a hardware constituent are changed, for example, from aninsulator to a conductor or vice versa. The instructions enable embeddedhardware (e.g., the execution units or a loading mechanism) to createmembers of the circuitry in hardware via the variable connections tocarry out portions of the specific operation when in operation.Accordingly, in an example, the machine-readable medium elements arepart of the circuitry or are communicatively coupled to the othercomponents of the circuitry when the device is operating. In an example,any of the physical components may be used in more than one member ofmore than one circuitry. For example, under operation, execution unitsmay be used in a first circuit of a first circuitry at one point in timeand reused by a second circuit in the first circuitry, or by a thirdcircuit in a second circuitry at a different time. Additional examplesof these components with respect to the device 500 follow.

In some aspects, the device 500 may operate as a standalone device ormay be connected (e.g., networked) to other devices. In a networkeddeployment, the communication device 500 may operate in the capacity ofa server communication device, a client communication device, or both inserver-client network environments. In an example, the communicationdevice 500 may act as a peer communication device in peer-to-peer (P2P)(or other distributed) network environment. The communication device 500may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, asmartphone, a web appliance, a network router, switch or bridge, or anycommunication device capable of executing instructions (sequential orotherwise) that specify actions to be taken by that communicationdevice. Further, while only a single communication device isillustrated, the term “communication device” shall also be taken toinclude any collection of communication devices that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein, such as cloudcomputing, software as a service (SaaS), and other computer clusterconfigurations.

Examples, as described herein, may include, or may operate on, logic ora number of components, modules, or mechanisms. Modules are tangibleentities (e.g., hardware) capable of performing specified operations andmay be configured or arranged in a certain manner. In an example,circuits may be arranged (e.g., internally or with respect to externalentities such as other circuits) in a specified manner as a module. Inan example, the whole or part of one or more computer systems (e.g., astandalone, client or server computer system) or one or more hardwareprocessors may be configured by firmware or software (e.g.,instructions, an application portion, or an application) as a modulethat operates to perform specified operations. In an example, thesoftware may reside on a communication device-readable medium. In anexample, the software, when executed by the underlying hardware of themodule, causes the hardware to perform the specified operations.Accordingly, the term “module” is understood to encompass a tangibleentity, be that an entity that is physically constructed, specificallyconfigured (e.g., hardwired), or temporarily (e.g., transitorily)configured (e.g., programmed) to operate in a specified manner or toperform part or all of any operation described herein. Consideringexamples in which modules are temporarily configured, each of themodules need not be instantiated at any one moment in time. For example,where the modules comprise a general-purpose hardware processorconfigured using software, the general-purpose hardware processor may beconfigured as respective different modules at different times. Thesoftware may accordingly configure a hardware processor, for example, toconstitute a particular module at one instance of time and to constitutea different module at a different instance of time.

Communication device (e.g., UE) 500 may include a hardware processor 502(e.g., a central processing unit (CPU), a graphics processing unit(GPU), a hardware processor core, or any combination thereof), a mainmemory 504, a static memory 506, and mass storage 507 (e.g., hard drive,tape drive, flash storage, or other block or storage devices), some orall of which may communicate with each other via an interlink (e.g.,bus) 508.

The communication device 500 may further include a display device 510,an alphanumeric input device 512 (e.g., a keyboard), and a userinterface (UI) navigation device 514 (e.g., a mouse). In an example, thedisplay device 510, input device 512 and UI navigation device 514 may bea touchscreen display. The communication device 500 may additionallyinclude a signal generation device 518 (e.g., a speaker), a networkinterface device 520, and one or more sensors 521, such as a globalpositioning system (GPS) sensor, compass, accelerometer, or anothersensor. The communication device 500 may include an output controller528, such as a serial (e.g., universal serial bus (USB), parallel, orother wired or wireless (e.g., infrared (IR), near field communication(NFC), etc.) connection to communicate or control one or more peripheraldevices (e.g., a printer, card reader, etc.).

The storage device 507 may include a communication device-readablemedium 522, on which is stored one or more sets of data structures orinstructions 524 (e.g., software) embodying or utilized by any one ormore of the techniques or functions described herein. In some aspects,registers of the processor 502, the main memory 504, the static memory506, and/or the mass storage 507 may be, or include (completely or atleast partially), the device-readable medium 522, on which is stored theone or more sets of data structures or instructions 524, embodying orutilized by any one or more of the techniques or functions describedherein. In an example, one or any combination of the hardware processor502, the main memory 504, the static memory 506, or the mass storage 516may constitute the device-readable medium 522.

As used herein, the term “device-readable medium” is interchangeablewith “computer-readable medium” or “machine-readable medium”. While thecommunication device-readable medium 522 is illustrated as a singlemedium, the term “communication device-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) configured to store theone or more instructions 524. The term “communication device-readablemedium” is inclusive of the terms “machine-readable medium” or“computer-readable medium”, and may include any medium that is capableof storing, encoding, or carrying instructions (e.g., instructions 524)for execution by the communication device 500 and that cause thecommunication device 500 to perform any one or more of the techniques ofthe present disclosure, or that is capable of storing, encoding orcarrying data structures used by or associated with such instructions.Non-limiting communication device-readable medium examples may includesolid-state memories and optical and magnetic media. Specific examplesof communication device-readable media may include: non-volatile memory,such as semiconductor memory devices (e.g., Electrically ProgrammableRead-Only Memory (EPROM), Electrically Erasable Programmable Read-OnlyMemory (EEPROM)) and flash memory devices; magnetic disks, such asinternal hard disks and removable disks; magneto-optical disks; RandomAccess Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples,communication device-readable media may include non-transitorycommunication device-readable media. In some examples, communicationdevice-readable media may include communication device-readable mediathat is not a transitory propagating signal.

The instructions 524 may further be transmitted or received over acommunications network 526 using a transmission medium via the networkinterface device 520 utilizing any one of a number of transferprotocols. In an example, the network interface device 520 may includeone or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) orone or more antennas to connect to the communications network 526. In anexample, the network interface device 520 may include a plurality ofantennas to wirelessly communicate using at least one ofsingle-input-multiple-output (SIMO), MIMO, ormultiple-input-single-output (MISO) techniques. In some examples, thenetwork interface device 520 may wirelessly communicate using MultipleUser MIMO techniques.

The term “transmission medium” shall be taken to include any intangiblemedium that is capable of storing, encoding or carrying instructions forexecution by the communication device 500, and includes digital oranalog communications signals or another intangible medium to facilitatecommunication of such software. In this regard, a transmission medium inthe context of this disclosure is a device-readable medium.

A communication device-readable medium may be provided by a storagedevice or other apparatus which is capable of hosting data in anon-transitory format. In an example, information stored or otherwiseprovided on a communication device-readable medium may be representativeof instructions, such as instructions themselves or a format from whichthe instructions may be derived. This format from which the instructionsmay be derived may include source code, encoded instructions (e.g., incompressed or encrypted form), packaged instructions (e.g., split intomultiple packages), or the like. The information representative of theinstructions in the communication device-readable medium may beprocessed by processing circuitry into the instructions to implement anyof the operations discussed herein. For example, deriving theinstructions from the information (e.g., processing by the processingcircuitry) may include: compiling (e.g., from source code, object code,etc.), interpreting, loading, organizing (e.g., dynamically orstatically linking), encoding, decoding, encrypting, unencrypting,packaging, unpackaging, or otherwise manipulating the information intothe instructions.

In an example, the derivation of the instructions may include assembly,compilation, or interpretation of the information (e.g., by theprocessing circuitry) to create the instructions from some intermediateor preprocessed format provided by the machine-readable medium. Theinformation, when provided in multiple parts, may be combined, unpacked,and modified to create the instructions. For example, the informationmay be in multiple compressed source code packages (or object code, orbinary executable code, etc.) on one or several remote servers. Thesource code packages may be encrypted when in transit over a network anddecrypted, uncompressed, assembled (e.g., linked) if necessary, andcompiled or interpreted (e.g., into a library, stand-alone executableetc.) at a local machine, and executed by the local machine.

Although an aspect has been described with reference to specificexemplary aspects, it will be evident that various modifications andchanges may be made to these aspects without departing from the broaderscope of the present disclosure. Accordingly, the specification anddrawings are to be regarded in an illustrative rather than a restrictivesense. This Detailed Description, therefore, is not to be taken in alimiting sense, and the scope of various aspects is defined only by theappended claims, along with the full range of equivalents to which suchclaims are entitled.

1-20. (canceled)
 21. An apparatus comprising: one or more processors forconfiguring a management service equipment for measuring a plurality ofkey performance indicators (KPIs) in a cellular network with a pluralityof network functions (NFs), the one or more processors are configured tocause the management service equipment to: retrieve a plurality ofperformance measurements associated with a cell of a radio accessnetwork (RAN) within the cellular network; generate a KPI of theplurality of KPIs associated with the cell, based on the plurality ofperformance measurements, wherein the plurality of performancemeasurements are related to one or more of: a number of handoverfailures, a number of resource control (RRC) connection setup failures,or a number of RACH procedure failures experienced for a predeterminedduration interval within the cell; and encode the KPI for transmission.22. The apparatus of claim 21, wherein the one or more processors areconfigured to cause the management service equipment to: retrieve theplurality of performance measurements from at least one NF of theplurality of NFs.
 23. The apparatus of claim 21, wherein the generatedKPI is a RAN condition KPI associated with a condition of RAN latency ofthe cell.
 24. The apparatus of claim 21, wherein the plurality ofperformance measurements comprise a number of radio resource control(RRC) connection setup failures experienced for a predetermined durationinterval within the cell.
 25. The apparatus of claim 21, wherein theplurality of performance measurements comprise a number of random accesschannel (RACH) procedure failures experienced for a predeterminedduration interval within the cell.
 26. The apparatus of claim 21,wherein the one or more processors are configured to cause themanagement service equipment to: retrieve alarm information orconfiguration information associated with communication conditions forthe cell; and generate the KPI of the plurality of KPIs associated withthe cell, further based on the alarm information or the configurationinformation.
 27. The apparatus of claim 26, wherein the alarminformation is a cell overload alarm indicating the cell is associatedwith more than a threshold number of active user equipment (UE) devices.28. The apparatus of claim 21, wherein the KPI is an integer indicatingat least one of the following communication conditions of the cell: anormal (healthy) cell, an out-of-service cell, a capacity constraintindicating an overloaded cell, and a capability constraint indicatingthe cell does not support latency requirements.
 29. The apparatus ofclaim 21, further comprising transceiver circuitry coupled to the one ormore processors and one or more antennas coupled to the transceivercircuitry, and wherein the one or more processors are configured tocause the management service equipment to: decode navigation informationreceived from an autonomous driving navigation application, thenavigation information indicating a planned navigation route through thecell and at least one neighboring cell; determine the KPI in response tothe received navigation information; and encode the KPI for transmissionto the autonomous driving-navigation application, the autonomousdriving-navigation application configured to modify the plannednavigation route based on the KPI.
 30. A non-transitory memory mediumfor operating a network node configured for generating a plurality ofkey performance indicators (KPIs) in a cellular network with a pluralityof network functions (NFs), wherein the memory medium stores programinstructions executable by one or more processors of the network nodeto: retrieve a plurality of performance measurements associated with acell of a radio access network (RAN) within the cellular network;generate a KPI of the plurality of KPIs associated with the cell, basedon the plurality of performance measurements, wherein the plurality ofperformance measurements are related to one or more of: a number ofhandover failures, a number of resource control (RRC) connection setupfailures, or a number of RACH procedure failures experienced for apredetermined duration interval within the cell; and encode the KPI fortransmission.
 31. The non-transitory memory medium of claim 30, whereinthe generated KPI is a RAN condition KPI associated with a condition ofRAN latency of the cell.
 32. The non-transitory memory medium of claim30, wherein the plurality of performance measurements comprise a numberof radio resource control (RRC) connection setup failures experiencedfor a predetermined duration interval within the cell.
 33. Thenon-transitory memory medium of claim 30, wherein the plurality ofperformance measurements comprise a number of random access channel(RACH) procedure failures experienced for a predetermined durationinterval within the cell.
 34. The non-transitory memory medium of claim30, wherein the KPI is an integer indicating at least one of thefollowing communication conditions of the cell: a normal (healthy) cell,an out-of-service cell, a capacity constraint indicating an overloadedcell, and a capability constraint indicating the cell does not supportlatency requirements.
 35. The non-transitory memory medium of claim 30,wherein the program instructions are further executable to: decodenavigation information received from an autonomous driving navigationapplication, the navigation information indicating a planned navigationroute through the cell and at least one neighboring cell; determine theKPI in response to the received navigation information; and encode theKPI for transmission to the autonomous driving-navigation application,the autonomous driving-navigation application configured to modify theplanned navigation route based on the KPI.
 36. A method for operating anetwork node configured for generating a plurality of key performanceindicators (KPls) in a cellular network with a plurality of networkfunctions (NFs), comprising: by the network node: retrieving a pluralityof performance measurements associated with a cell of a radio accessnetwork (RAN) within the cellular network; generating a KPI of theplurality of KPIs associated with the cell, based on the plurality ofperformance measurements, wherein the plurality of performancemeasurements are related to a number of handover failures experiencedwithin the cell; and encoding the KPI for transmission.
 37. The methodof claim 36, wherein the generated KPI is a RAN condition KPI associatedwith a condition of RAN latency of the cell.
 38. The method of claim 36,wherein the plurality of performance measurements comprise a number ofradio resource control (RRC) connection setup failures experienced for apredetermined duration interval within the cell.
 39. The method of claim36, wherein the plurality of performance measurements comprise a numberof random access channel (RACH) procedure failures experienced for apredetermined duration interval within the cell.
 40. The method of claim36, further comprising: decoding navigation information received from anautonomous driving navigation application, the navigation informationindicating a planned navigation route through the cell and at least oneneighboring cell; determining the KPI in response to the receivednavigation information; and encoding the KPI for transmission to theautonomous driving-navigation application, the autonomousdriving-navigation application configured to modify the plannednavigation route based on the KPI.